-
Notifications
You must be signed in to change notification settings - Fork 236
[0.2.x]: Fix warning, remove #[deny(warnings)] but keep check on CI #214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @ryankurte (rust_highfive has picked a reviewer for you, use r? to override) |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm thanks, and agreed on the cherry pick if you'd like to PR this?
bors r+ |
214: [0.2.x]: Fix warning, remove #[deny(warnings)] but keep check on CI r=ryankurte a=eldruin This fixes #213. Additionally I removed #[deny(warnings)] but added a check for it on CI. I think we should cherry pick #138 to the 0.2.x branch as well and release a 0.2.4 version, since 1.0 will still take a while. I can do that in a separate PR. Co-authored-by: Diego Barrios Romero <[email protected]>
Build failed: |
CI tests failed on rust nightly due to untagged-option. I have updated the |
@ryankurte Could you retry? Travis seems not to have run after I updated the dependency. |
bors retry |
🔒 Permission denied Existing reviewers: click here to make adamgreig a reviewer |
bors retry |
Build succeeded: |
This fixes #213. Additionally I removed #[deny(warnings)] but added a check for it on CI.
I think we should cherry pick #138 to the 0.2.x branch as well and release a 0.2.4 version, since 1.0 will still take a while.
I can do that in a separate PR.